home *** CD-ROM | disk | FTP | other *** search
- Path: tudelft.nl!news
- From: Ejo Schrama <schrama@geo.tudelft.nl>
- Newsgroups: comp.lang.c++
- Subject: Re: stack overflow
- Date: 13 Jan 1996 09:41:01 GMT
- Organization: TU Delft
- Message-ID: <4d7und$d2v@mo6.rc.tudelft.nl>
- References: <1996Jan7.231111.111385@kuhub.cc.ukans.edu> <4d3npc$d9m@news.bridge.net>
- NNTP-Posting-Host: ge8.geo.tudelft.nl
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 1.22 (Windows; I; 16bit)
-
- David Byrden <100101.2547@compuserve.com> wrote:
- >
- >Stack overflow means the program used more stack space than was
- >available. A portion of the stack is used each time you enter a
- >function, it is where the automatic locals go. It is releaased
- >when you return.
- >
- >You may simply need to recompile or relink and specify a larger
- >stack, or you may have a bug causing a function to call itself
- >eternally.
- >
- > David
- >
- >
-
- The problem stack overflow may also be caused by compiler limitations.
- Example: I'm working on a rather large orbit determination program,
- many classes, many routines and some with internal tables. Result:
- it runs perfectly fine under unix, (HP/UX), but categorically refuses
- to run under borland 3.1, even the dos version. Reason: the stack
- has to fit within one code segment. Remedy: i'm going to try something
- else than borland's 3.1 compiler, possibly djgpp.
-
- Ejo
-
-